Tele-presence robot system with multi-cast features

ABSTRACT

A graphical user interface for a remote controlled robot system that includes a robot view field that displays information provided by a robot and an observer view field that display observer information about one or more observers that can receive the robot information. The interface has various features that allow a master user to control the observation and participation of the observers.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The subject matter disclosed generally relates to the field of robotics.

2. Background Information

Robots have been used in a variety of applications ranging from remote control of hazardous material to assisting in the performance of surgery. For example, U.S. Pat. No. 5,762,458 issued to Wang et al. discloses a system that allows a surgeon to perform minimally invasive medical procedures through the use of robotically controlled instruments. One of the robotic arms in the Wang system moves an endoscope that has a camera. The camera allows a surgeon to view a surgical area of a patient.

There has been marketed a mobile tele-presence robot introduced by InTouch Technologies, Inc., the assignee of this application, under the trademark RP-7. The InTouch robot is controlled by a user at a remote station. The remote station may be a personal computer with a joystick that allows the user to remotely control the movement of the robot. Both the robot and remote station have cameras, monitors, speakers and microphones to allow for two-way video/audio communication. The robot camera provides video images to a screen at the remote station so that the user can view the robot's surroundings and move the robot accordingly.

U.S. Pat. No. 7,158,860 issued to Wang et al. and assigned to the owner of the present application, InTouch Technologies, Inc. discloses a tele-presence robot system that includes a primary remote control station and one or more secondary control stations that are all linked to a tele-presence robot. The system allows the secondary stations to observe the video/audio feed provided by the robot. This allows the users of the secondary station to be trained through the robot and primary station. It would be desirable to modify such a system to implement more features such as the ability for two-way communication between stations, or the transfer of robot control to one of the secondary stations.

BRIEF SUMMARY OF THE INVENTION

A graphical user interface for a remote controlled robot system that includes a robot view field that displays information provided by a robot and an observer view field that displays observer information about one or more observers that can receive the robot information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a robotic system;

FIG. 2 is a schematic of an electrical system of a robot;

FIG. 3 is side view of the robot;

FIG. 4 is a schematic of a robotic system wherein multiple remote stations are coupled to the robot;

FIG. 5 is an illustration of a user interface;

FIG. 6 is an illustration of a message popup of the user interface;

FIGS. 7A-C are illustrations of graphical messages;

FIG. 8 is an illustration of the user interface shown in FIG. 5 with a pull-down menu;

FIG. 9 is an illustration showing a user interface for an observer remote control station;

FIG. 10 is an illustration similar to FIG. 5 showing microphone volume control features;

FIG. 11 is an illustration of a dialog box showing bandwidth requirement of the system during a session;

FIG. 12 is a side view of a robot head.

DETAILED DESCRIPTION

Disclosed is a graphical user interface for a remote controlled robot system that includes a robot view field that displays information provided by a robot and an observer view field that displays observer information about one or more observers that can receive the robot information. The interface has various features that allow a master user to control the observation and participation of observers.

Referring to the drawings more particularly by reference numbers, FIG. 1 shows an embodiment of robot system 10. The robot system 10 includes a robot 12, a base station 14 and a plurality of remote control stations 16. Each remote control station 16 may be coupled to the base station 14 through a network 18. By way of example, the network 18 may be either a packet switched network such as the Internet, or a circuit switched network such has a Public Switched Telephone Network (PSTN) or other broadband system. The base station 14 may be coupled to the network 18 by a modem 20 or other broadband network interface device.

Each remote control station 16 may include a computer 22 that has a monitor 24, a camera 26, a microphone 28 and a speaker 30. The computer 22 may also contain an input device 32 such as a joystick or a mouse. Each control station 16 is typically located in a place that is remote from the robot 12. Although only one robot 12 is shown, it is to be understood that the system 10 may have a plurality of robots 12. In general any number of robots 12 may be controlled by any number of remote stations. For example, one remote station 16 may be coupled to a plurality of robots 12, or one robot 12 may be coupled to a plurality of remote stations 16.

The robot 12 includes a movement platform 34 that is attached to a robot housing 36. Also attached to the robot housing 36 are a camera 38, a monitor 40, a microphone(s) 42 and a speaker 44. The microphone 42 and speaker 30 may create a stereophonic sound. The robot 12 may also have an antenna 46 that is wirelessly coupled to an antenna 48 of the base station 14. The system 10 allows a user at the remote control station 16 to move the robot 12 through the input device 32. The robot camera 38 is coupled to the remote monitor 24 so that a user at the remote station 16 can view a patient. Likewise, the robot monitor 40 is coupled to the remote camera 26 so that the patient can view the user. The microphones 28 and 42, and speakers 30 and 44, allow for audible communication between the patient and the user.

Each remote station computer 22 may operate Microsoft OS software and WINDOWS XP or other operating systems such as LINUX. The remote computer 22 may also operate a video driver, a camera driver, an audio driver and a joystick driver. The video images may be transmitted and received with compression software such as MPEG CODEC.

FIGS. 2 and 3 show an embodiment of the robot 12. The robot 12 may include a high level control system 50 and a low level control system 52. The high level control system 50 may include a processor 54 that is connected to a bus 56. The bus is coupled to the camera 38 by an input/output (I/O) port 58, and to the monitor 40 by a serial output port 60 and a VGA driver 62. The monitor 40 may include a touchscreen function that allows the patient to enter input by touching the monitor screen.

The speaker 44 is coupled to the bus 56 by a digital to analog converter 64. The microphone 42 is coupled to the bus 56 by an analog to digital converter 66. The high level controller 50 may also contain random access memory (RAM) device 68, a non-volatile RAM device 70 and a mass storage device 72 that are all coupled to the bus 62. The mass storage device 72 may contain medical files of the patient that can be accessed by the user at the remote control station 16. For example, the mass storage device 72 may contain a picture of the patient. The user, particularly a health care provider, can recall the old picture and make a side by side comparison on the monitor 24 with a present video image of the patient provided by the camera 38. The robot antennae 46 may be coupled to a wireless transceiver 74. By way of example, the transceiver 74 may transmit and receive information in accordance with IEEE 802.11b.

The controller 54 may operate with a LINUX OS operating system. The controller 54 may also operate MS WINDOWS along with video, camera and audio drivers for communication with the remote control station 16. Video information may be transceived using MPEG CODEC compression techniques. The software may allow the user to send e-mail to someone at the robot site and vice versa, or allow someone at the robot site to access the Internet. In general the high level controller 50 operates to control the communication between the robot 12 and the remote control station 16.

The high level controller 50 may be linked to the low level controller 52 by serial port 76. The low level controller 52 runs software routines that mechanically actuate the robot 12. For example, the low level controller 52 provides instructions to actuate the movement platform to move the robot 12. The low level controller 52 may receive movement instructions from the high level controller 50. The movement instructions may be received as movement commands from the remote control station. Although two controllers are shown, it is to be understood that the robot 12 may have one controller controlling the high and low level functions.

FIG. 3 shows an embodiment of the robot 12. The robot 12 may include a holonomic platform 110 that is attached to a robot housing 112. The holonomic platform 110 provides three degrees of freedom to allow the robot 12 to move in any direction.

The robot 12 may have a head 114 that supports the camera 38 and the monitor 40. The head 114 may have two degrees of freedom so that the camera 26 and monitor 24 can swivel and pivot as indicated by the arrows.

The system may be the same or similar to a robot system provided by the assignee InTouch-Health, Inc. of Santa Barbara, Calif. under the trademark RP-7. The system may also be the same or similar to the system disclosed in U.S. Pat. No. 6,925,357 issued Aug. 2, 2005, which is hereby incorporated by reference.

In operation, the robot 12 may be placed in a home, public or commercial property, or a facility where one or more patients are to be monitored and/or assisted. The facility may be a hospital or a residential care facility. By way of example, the robot 12 may be placed in a home where a health care provider may monitor and/or assist the patient. Likewise, a friend or family member may communicate with the patient. The cameras and monitors at both the robot and remote control stations allow for teleconferencing between the patient and the person at the remote station(s).

The robot 12 can be maneuvered through the home, property or facility by manipulating the input device 32 at a remote station 16.

The robot 10 may be controlled by a number of different users. To accommodate for this the robot may have an arbitration system. The arbitration system may be integrated into the operating system of the robot 12. For example, the arbitration technique may be embedded into the operating system of the high-level controller 50.

By way of example, the users may be divided into classes that include the robot itself, a local user, a caregiver, a doctor, a family member, or a service provider. The robot 12 may override input commands that conflict with robot operation. For example, if the robot runs into a wall, the system may ignore all additional commands to continue in the direction of the wall. A local user is a person who is physically present with the robot. The robot could have an input device that allows local operation. For example, the robot may incorporate a voice recognition system that receives and interprets audible commands.

A caregiver is someone who remotely monitors the patient. A doctor is a medical professional who can remotely control the robot and also access medical files contained in the robot memory. The family and service users remotely access the robot. The service user may service the system such as by upgrading software, or setting operational parameters.

Message packets may be transmitted between a robot 12 and a remote station 16. The packets provide commands and feedback. Each packet may have multiple fields. By way of example, a packet may include an ID field a forward speed field, an angular speed field, a stop field, a bumper field, a sensor range field, a configuration field, a text field and a debug field.

The identification of remote users can be set in an ID field of the information that is transmitted from the remote control station 16 to the robot 12. For example, a user may enter a user ID into a setup table in the application software run by the remote control station 16. The user ID is then sent with each message transmitted to the robot.

The robot 12 may operate in one of two different modes; an exclusive mode, or a sharing mode. In the exclusive mode only one user has access control of the robot. The exclusive mode may have a priority assigned to each type of user. By way of example, the priority may be in order of local, doctor, caregiver, family and then service user. In the sharing mode two or more users may share access with the robot. For example, a caregiver may have access to the robot, the caregiver may then enter the sharing mode to allow a doctor to also access the robot. Both the caregiver and the doctor can conduct a simultaneous tele-conference with the patient.

The arbitration scheme may have one of four mechanisms; notification, timeouts, queue and call back. The notification mechanism may inform either a present user or a requesting user that another user has, or wants, access to the robot. The timeout mechanism gives certain types of users a prescribed amount of time to finish access to the robot. The queue mechanism is an orderly waiting list for access to the robot. The call back mechanism informs a user that the robot can be accessed. By way of example, a family user may receive an e-mail message that the robot is free for usage. Tables 1 and 2, show how the mechanisms resolve access request from the various users.

TABLE I Access Medical Command Software/Debug Set User Control Record Override Access Priority Robot No No Yes (1) No No Local No No Yes (2) No No Caregiver Yes Yes Yes (3) No No Doctor No Yes No No No Family No No No No No Service Yes No Yes Yes Yes

TABLE II Requesting User Local Caregiver Doctor Family Service Current Local Not Allowed Warn current user of Warn current user of Warn current user of Warn current user of User pending user pending user pending user pending user Notify requesting user Notify requesting user Notify requesting user Notify requesting user that system is in use that system is in use that system is in use that system is in use Set timeout Set timeout = 5 m Set timeout = 5 m No timeout Call back Call back Caregiver Warn current user of Not Allowed Warn current user of Warn current user of Warn current user of pending user. pending user pending user pending user Notify requesting user Notify requesting user Notify requesting user Notify requesting user that system is in use. that system is in use that system is in use that system is in use Release control Set timeout = 5 m Set timeout = 5 m No timeout Queue or callback Callback Doctor Warn current user of Warn current user of Warn current user of Notify requesting user Warn current user of pending user pending user pending user that system is in use pending user Notify requesting user Notify requesting user Notify requesting user No timeout Notify requesting user that system is in use that system is in use that system is in use Queue or callback that system is in use Release control Set timeout = 5 m No timeout No timeout Callback Callback Family Warn current user of Notify requesting user Warn current user of Warn current user of Warn current user of pending user that system is in use pending user pending user pending user Notify requesting user No timeout Notify requesting user Notify requesting user Notify requesting user that system is in use Put in queue or that system is in use that system is in use that system is in use Release Control callback Set timeout = 1 m Set timeout = 5 m No timeout Queue or callback Callback Service Warn current user of Notify requesting user Warn current user of Warn current user of Not Allowed pending user that system is in use request pending user Notify requesting user No timeout Notify requesting user Notify requesting user that system is in use Callback that system is in use that system is in use No timeout No timeout No timeout Callback Queue or callback

The information transmitted between the station 16 and the robot 12 may be encrypted. Additionally, the user may have to enter a password to enter the system 10. A selected robot is then given an electronic key by the station 16. The robot 12 validates the key and returns another key to the station 16. The keys are used to encrypt information transmitted in the session.

FIG. 4 shows a system with a plurality of remote stations 16A, 16B and 16C that can access a robot 12 through the network 18. The system can be set into a session mode wherein a master remote station 16A controls movement of the robot and receives both video and audio information from the robot camera and speaker, respectively. The observer stations 16B and 16C may also receive audio and visual information transmitted between the robot 12 and the station 16A. This mode allows multiple users at stations 16B and 16C to observe use of the robot while a teacher or master at station 16A moves the robot.

During a session the master remote station 16A can retransmit the audio/visual information received from the robot 12 to the observer stations 16B and 16C. This can be done by changing the ID(s) in the ID field of the data packets received from the robot and then retransmitting the packets to the observer stations. Alternatively, the master remote station 16A can instruct the robot to transmit the audio and visual information to the master 16A, and the observer 16B and 16C remote stations. It being understood that each remote station 16A, 16B and 16C has a unique network identifier such as an IP address that allows the robot to direct information to each station. The packets may contain a BROADCAST field that contains the station IDs for the remote stations that are to receive packets from the robot. The BROADCAST field may be filled by the master station 16A.

The session mode allows for training through the robot. For example, the master remote station 16A may be operated by a physician who moves the robot into visual and audio contact with a patient. The observer remote stations 16B an 16C may be manned by personnel such as interns that observe and receive instructional training on providing care giving to the patient. Although instruction of medical personnel is described, the system can be used to train any group of users that are remotely located from a training area. For example, the system may be used to train personnel at a department store or allow potential buyers of real estate property to remotely view the property.

FIG. 5 shows a display user interface (“DUI”) 200 displayed at the master control station 16A. The DUI 200 may include a robot view field 202 that displays a video image captured by the camera of the robot. The DUI 200 may also include a station view field 204 that displays a video image provided by the camera of the master remote station 16A. The DUI 200 may be part of an application program stored and operated by the computer 22 of the remote station 16A.

The DUI 200 may include a “Connect” button 206 that can be selected to connect the station to a robot. Selection of the Connect button 206 may cause the display of pull-down screens, etc. that allow the user to select a desired robot. System settings and options can be selected through buttons 208 and 210, respectively.

One of the options is to allow for multicasting. FIG. 6 shows a menu 212 with an “Enable Multicasting” box 214 that can be “checked” to allow for other remote station to join a multi-cast session.

A user at an observer station may attempt a connection with the same robot. If a robot is already in use the screen may display a message box 216 as shown in FIG. 7A. The message box 216 includes an “OK” button 218 that allows the user to request joining the session as an observer. If the user presently connected to the robot has not enabled the multicasting feature then a message 220 may be displayed indicating this fact as shown in FIG. 7B. If the user selected the OK button 218 then the master user may receive the message 222 shown in FIG. 7C. The message includes an “Accept” button 224 and a “Deny” button 226 that allows the master user to accept or deny the request to observe the session, respectively. When an observer is accepted the observers may receive the audio/video feeds from by the robot.

User's that are accepted are displayed in an observer view field 228 of the master control station DUI 200 shown in FIG. 5. The field 228 can provide video images of the users captured by the cameras of the observer remote control stations. Each video image may also include a caption of the observer's name. The field includes a scroll down tab 230 that allows the master user to scroll down the video images of the observers.

The master user can right click on any observer video image to display the pull down menu 232 shown in FIG. 8.

The pull down menu 228 allows the master user to select various options for the selected observer. The pull down menu 232 includes an “Allow The Robot To Hear This User” feature 234 that can be selected so that the observer can provide audio to the robot. The system may allow for simultaneous three way audio between the robot, master user and one observer. Both the master and the observer stations include a “Push To Talk” icon 236. If there is more than one observer then the “Push To Talk” icon 236 is enabled and the observer must continuously select the icon 232 to talk, much like a walkie-talkie button. The space bar may also be pushed after the icon 236 is selected to allow audio communication to the robot. When Push To Talk is selected then an icon 238 can be displayed in the observers video image to indicate which observer is providing audio input to the robot. The master and observer stations may also have a “Local Talk” icon 240.

Selecting the Local Talk icon allows for textual communication between just the remote stations, popping up a text chat dialog box within each interface, which allows the master and observers to exchange text messages. Prior to displaying the text chat dialog box, a popup dialog box (not shown) may be displayed to the user who initiated Local Talk, which would list all current session participants, and allow the user to select only those participants to be part of the Local Talk. There may be a “Limit Voice” box (not shown) that can be selected to limit audio output of participants in the local chat to only those other remote stations participating in the local chat.

An “Allow Robot To See This User” feature 242 can be selected so that the observer's video image is provided to the monitor of the robot instead of the master user's video image. The observer's video image may be displayed in the station view field 204 when that observer's image is provided to the robot. The “Allow This User To See Robot Video” 244 and “Allow This User To Hear Robot Audio” features 246 can be selected so that the observer receives the video and audio feeds from the robot, respectively.

The “Head Control” feature 248 allows the selected observer to control the robot head to move the robot camera. The “Driving” feature 250 allows the observer to drive the robot. When the Driving feature is selected robot data such as position sensor data, battery power, etc. are provided to the selected observer's remote station. The “Camera & Aux Video Control” feature 252 allows the observer to control robot camera functions such as zoom, brightness, etc. The master no longer has the head, driving and camera controls when these features are transferred to an observer.

The menu 232 includes a “Telestration” feature 254 that allows an observer to annotate an image provided by to robot. For example, the image can be a document or an X-ray. An observer can annotate the image, for example to circle and area of the X-ray to help communicate with a patient at the robot site. The master or any observer can enable a cursor function by selecting a “Live Cursor” icon 256. Selecting the icon 256 allows the user to move a cursor 258 that is overlayed on the robot video image. The cursor 258 is provided on the image field 202 for all remote stations in a session. The master and observers can each be designated a different color so that different cursors can be distinguished by the users. The cursor color 260 can be displayed in the video image of the master or the observer.

The robot may connected to a medical instrument such as a stethoscope. The “Stethescope” feature 262 of the pull down menu 232 allows the observers to receive instrument input from the stethoscope. The menu 232 may have a “Give This User Master Control” feature 264 that allows the selected observer to become a master user. The master can also disconnect an observer by selecting the “Disconnect This User” feature 266.

FIG. 9 shows a user interface 270 for observer. The interface does not include robot control functions unless enabled by the master user. The interface 270 is similar to the master DUI 200, but lacks certain robot controls.

Referring again to FIG. 5, both the robot view field 202 and the station view field 204 may have associated graphics to vary the video and audio displays. For example, each field may have graphical slide bars 280 and 282 to vary the zoom and brightness of the cameras, respectively. A still picture may be taken at either the robot or remote station by selecting one of the graphical camera icons 284. The still picture may be the image presented at the corresponding field 202 or 204 at the time the camera icon 284 is selected. Capturing and playing back video can be taken through graphical icons 286. A return to real time video can be resumed, after the taking of a still picture, captured video, or reviewing a slide show, by selecting a graphical LIVE button 288.

The local controls can include slide bars for the local station speaker 290 and microphone 292. Also displayed is a microphone meter icon 294 that varies with the volume of the user's voice. The robot volume may be different from the user's input volume. The remote controls also includes a microphone meter icon 296 that represents the user's audio volume at the robot. The robot may have a local volume control so that user's at the robot site can vary the robot speaker volume. Normally the meter icons 294 and 296 will represent essentially the same value. The robot volume may be different from the user's input volume, for example, if the robot local volume control is adjusted the at the robot site. As shown in FIG. 10, if this occurs the volume slide bar 292 may be enabled to allow the user to vary the microphone. The DUI may also display a “Reset” button 298 that can be selected to automatically reset the robot speaker volume to a center position.

Referring to FIG. 5, the robot view field 202 may include a “Video Mute To Robot” feature 300 which when selected prevents audio and video transmission to the robot from all remote stations. Field 202 may also have a “Master/Robot Privacy” feature 302 that can prevent the observer stations from receiving robot video and audio from both the robot and the master control station.

The master user can also be allowed to control the bandwidth of the system by controlling the video feeds to the observer stations. FIG. 11 shows a dialog box 310 that displays the bandwidth usage of various participants in a session, along with network health parameters such as packet losses and jitter between participants. “Drop Vid” buttons 312 may be placed next to observer stations so that the master user can drop a particular observer's video.

FIG. 12 shows a non-mobile robot head 320 that can both pivot and spin the camera 38 and the monitor 40. The robot head 320 can be similar to the robot 12 but without the platform 110. The robot head 320 may have the same mechanisms and parts to both pivot the camera 38 and monitor 40 about a pivot axis 4, and spin the camera 38 and monitor 40 about a spin axis 5. The pivot axis may intersect the spin axis. Having a robot head 320 that both pivots and spins provides a wide viewing area. The robot head 320 may be in the system either with or instead of the mobile robot 12.

The system may have numerous applications. For example, a physician intensivist may initiate a remote presence session with a robot in order to diagnose a patient in an Emergency Room. Upon examining the patient, the physician may realize that the patient assessment will require consultation by a neurology specialist. The intensivist calls the neurologist by phone, asking him to join the session. Upon receiving the telephone request, the neurologist opens his laptop, selects the robot in question from the robot list in the interface, and clicks “Connect”. Seeing the message in FIG. 7A, he clicks “OK” and then sees the message in FIG. 7B. The intensivist meanwhile sees the message in FIG. 7C and clicks “Accept”. At this point the neurologist receives the robot video and can hear both the robot-side audio and the intensivist.

The intensivist uses the Live Cursor to point to the patient's face and EEG data on a wall. The neurologist obtains background information that can be provided by a nurse standing next to the patient and in front of the robot, as well as ICU-specific information provided by the intensivist on the master control station. Then, the neurologist can provide an audio assessment of the patient's condition. The intensivist then right-clicks on the thumbnail image of the neurologist in field 288, and clicks the appropriate features in the pull-down menu to allow the neurologist to be seen and heard on the robot. The neurologist can then inform both the patient and family of the condition.

In another application, a surgeon may be logged onto a robot and performing rounds in patient rooms within a hospital. Residents from hospitals in other cities join the session in the manner described above. The surgeon describes what he is doing to the residents, who may ask questions, and thereby learn the best way to round patients.

In another application, a hospital CEO may connect to the robot, and telephones three prospective doctors whom the hospital is courting to join the staff. These doctors each join the session as discussed above. The CEO then uses the joystick to drive the robot through the hospital, performing a virtual tour, and discusses the facility with the observer physicians.

In yet another application, a sales VP of an MRI manufacturing company may connect to a robot in the laboratory wing of a hospital, and then phones the COO of a different hospital to join the session. Upon joining, the sales VP drives the robot into the MRI lab and drives around the MRI machine, describing its features. An on-site MRI technician operates certain controls on the direction of the sales VP. The sales VP explains to the COO the various benefits of purchasing the MRI machine.

While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other modifications may occur to those ordinarily skilled in the art. 

What is claimed is:
 1. A graphical user interface for a remote controlled robot system, comprising: a robot view field that displays information provided by a robot; an observer view field that displays observer information about one or more observers that can receive the robot information.
 2. The interface of claim 1, wherein said robot information is video provided by a robot camera.
 3. The interface of claim 1, further comprising a station view field that display video provided by a camera of a remote control station.
 4. The interface of claim 1, further comprising one or more messages that allow an observer to join a session.
 5. The interface of claim 1, further comprising a selectable feature that controls a transmission of audio from an observer remote control station to said robot.
 6. The interface of claim 1, further comprising a selectable feature that controls a transmission of video from an observer remote control station to said robot.
 7. The interface of claim 1, further comprising a selectable feature that controls a transmission of audio from said robot to an observer remote control station.
 8. The interface of claim 1, further comprising a selectable feature that controls a transmission of video from said robot to an observer remote control station.
 9. The interface of claim 1, further comprising a selectable feature that allows an observer remote control station to control a movement of said robot.
 10. The interface of claim 1, further comprising a selectable feature that allows an observer remote control station to control at least one camera parameter of said robot.
 11. The interface of claim 1, further comprising a selectable feature that allows an observer remote control station to receive instrument data from an instrument coupled to said robot.
 12. The interface of claim 2, further comprising a selectable feature that allows an observer remote control station to annotate said robot videos, said annotation being displayed in said robot view field.
 13. The interface of claim 1, further comprising a selectable feature that allows an observer remote control station to become a master remote control station.
 14. The interface of claim 1, further comprising a selectable feature that disconnects an observer remote control station.
 15. The interface of claim 1, wherein said observer view field displays a video image provided by an observer remote control station.
 16. The interface of claim 1, further comprising a dialog box that displays a system bandwidth usage and allows a user to vary said system bandwidth usage.
 17. The interface of claim 1, further comprising a selectable feature that allows communication only between a plurality of remote control stations.
 18. A graphical user interface for a remote controlled robot system, comprising: a robot view field that displays information provided by a robot; a local microphone meter that represents a volume of audio provided to a microphone of a remote control station; and, a remote microphone meter that represents a volume of audio generated by a robot speaker.
 19. The interface of claim 18, further comprising a selectable feature that can reset a robot speaker volume.
 20. The interface of claim 18, further comprising a selectable feature to vary a volume of said remote control station microphone. 